Skip to content

Conversation

x15sr71
Copy link

@x15sr71 x15sr71 commented Sep 5, 2025

Fixes critical macOS build failures that were preventing development on modern macOS systems.

Resolves: #11


Problem

  • BUILD FAILED on macOS due to outdated deployment target (10.12)
  • Missing CocoaPods integration causing framework linking errors
  • Incompatibility with modern Xcode versions and Apple Silicon hardware

Solution

Fixed Deployment Target

  • Updated MACOSX_DEPLOYMENT_TARGET from 10.12 → 10.15
  • Ensures compatibility with modern SDKs and build tools

Added CocoaPods Integration

  • Configured Xcode project with CocoaPods build phases and base configurations
  • Added workspace reference to Pods project for proper framework linking
  • Enables Firebase SDK dependencies to link correctly

Modernized Swift Code

  • Updated AppDelegate.swift: replaced @NSApplicationMain@main
  • Implemented applicationSupportsSecureRestorableState for modern lifecycle support

Updated Dependencies

  • Upgraded flutter_local_notifications to v19.4.1 for compatibility
  • Added Windows plugin support for cross-platform consistency

Screenshots

Click to view successful build & app launch Screenshot 2025-09-05 at 8 11 16 PM

Environment Tested

  • macOS: 15.6.1 (24G90)
  • Chip: Apple M4 Pro (ARM64)
  • Xcode: 16.4 (Build 16F6)
  • Flutter: 3.35.2
  • CocoaPods: 1.16.2

Testing

  • Fresh clone → build succeeds on macOS
  • flutter run -d macos launches app successfully
  • Firebase SDK initializes without linking errors
  • No CocoaPods warnings or mismatched deployment targets

Notes & Remaining Warnings

During testing, some non-critical warnings still appear from CocoaPods build phases, e.g.:

warning: Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs.

These warnings come from Pods such as abseil, BoringSSL-GRPC, gRPC-Core, gRPC-C++, etc.

These are not critical to the purpose of this PR, which is focused on fixing the macOS build failures.
They can be safely addressed in a future cleanup PR.

  • Changes are scoped only to macOS build system + dependencies
  • No app logic or UI changes were introduced
  • Safe for merge without affecting iOS/Android builds

👋 Hi, I’m Chandragupt, a new contributor to CCExtractor.
This PR is my first step towards improving macOS compatibility for the firebase_editor project.

@x15sr71 x15sr71 changed the title fix(macos): resolve build failures and deployment target issues fix(macOS): resolve build failures and deployment target issues Sep 6, 2025
@chiragtyagi2003
Copy link
Collaborator

chiragtyagi2003 commented Sep 6, 2025 via email

@x15sr71
Copy link
Author

x15sr71 commented Sep 6, 2025

Hey @chiragtyagi2003,
Sounds good, no worries! I'll wait for your review whenever you're back at your system.

Thanks for letting me know!

@x15sr71
Copy link
Author

x15sr71 commented Sep 18, 2025

Hello @chiragtyagi2003, just a gentle reminder regarding this PR. Your review when convenient would be much appreciated.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants